Based on a lot of things that have been said here there is several things you should check.
1) Zoning is setup proper 2) Switch is hard set for 4gb and not on Auto 3) Are the tape drives in use when you are trying to do this? (belive it or not this matters.)
Inquire although useful, will display different information back to a server connected to the same drives, if those drives are in use on a different server. So make sure none of the hardware is in use.
I myself have tried to setup drives on a storage node in the past, and scratched my head as to why doesn't the server see them, and why arent they appearing in inquire, only to come and find out they were in use.
4) Open your HBA software and see if the drives appear there. If they don't, or only one of them does. You need to go back to the switch. OS won't see them if the HBA can't see them.
I am able to see only one tape drive like IBM ULTRIUM. I should have ADIC drive for jukebox as, and second IBMUltrium drive. The idea is that this driver has to install by itself I guess.
Well yes, Windows install drivers itself provided it is able to detect the devices. For each Autochanger you should have a medium changer and all the devices connected to the server. You can try and rescan for hardware changes to be sure.
If it is not there, check the hardware connectivity. reboot the server and check during boot process on the SCSI card if I think cabling is OK.
I would also recommend installing latest Autochanger & device manufacturer drivers instead of relying on Windows drivers.
"If it is not there, check the hardware connectivity. reboot the server and check during boot process on the SCSI card if I think cabling is OK"
Ok with drivers, but I have checked Connectrix and zone for that, and it seems to be OK. HBAnywhere as well. But what about SCSI card? I have on Device Manager SCSI and RAID controllers and there is EMS Device bus.
Briefly I do not have knowledge to know how to check cabling on SCSI card!
you need to know how is the library connected to your server. if it has worked before you have a device or cabling malfunction. if it is the first time setup most likely you have improper cabling or zoning. use the HBA or SCSI tools to scan the controller for the devices. once you see it there it will be in device manager. until you can see it in device manager you do not need to try to resolve it on networker level.
If your using Fiber drives. You need to assign one of the drives as the controlling drive. Least thats what I did in my Dell Branded ADIC i500 scalar library.
If this tape drive that is the controller is not presented to the server (Management Server or Storage Node), server won't see the library. Only server to see the library would then be the machine that has that tape drive presented to it. (Zoned to that server)
Since you did not mention whether library is SCSI or FC, I assumed it to be SCSI. If it is FC, you do not need to check that. All you need on OS is to make sure you get the library robotics and the tape devices as medium changer & Tape Drives in the Device Manager. Library Robotics is mandatory only if this server is controlling the robotics.
Run the inquire command and check if you get the robotics and drives there. If not clear to you, post the output here.
The same thing is on the Device manager. This is new computer and it is storage node. It works only for one drive (device). I have installed Ultrium Driver.
Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\mb_admin> That one is storage node as well, but I can have two devices (two drives on the jukebox) from this server.The Device Manager gives drive for a changer and two drives for tape. Therefore I can have two devices for each old sever configured as a storage node.
If the first output is of the storage node in question and the same is visible in Device Manager, then the problem is with the OS & device drivers.
Do you see the second drive & medium changer as unknown devices in Device Manager? If not, you have issues with the setup somewhere. When I had zoning done properly but devices not visible in the Device Manager, I checked that the FC ports on switch were on Auto mode. I could resolve the problem when I switched them to 4 Gbps from Auto mode.
Also note, the reason you may not be seeing the jukebox is because the drive that is not appearing, is the controller path drive for the medium changer, and there fore would not be showing up. Once you get that other drive to appear, I am guessing your jukebox will appear at the same time.
"1) Zoning is setup proper 2) Switch is hard set for 4gb and not on Auto 3) Are the tape drives in use when you are trying to do this? (belive it or not this matters.)"
Zoning is Ok. Switch is DS 4700M, and the speed is 4Gb. It set for negotiate. No tape drives are not in use for sure.
4) Open your HBA software and see if the drives appear there. If they don't, or only one of them does. You need to go back to the switch. OS won't see them if the HBA can't see them.
That might be prtoblem, HBAnyware - on the first dapter. I have got message:" WWN list is not available when automap is disabled". On the target mapping I have automapping disabled. Now I have to be sure to put automapping enabled. On th etop of that I have to think about persistant binding because I have windows 2003 servers.
Persistent binding is another issusing I became ohhhhh so familiar with when it comes to windows.
If you allow me to digress from the topic a hair here, I will give you some helpful information.
I believe from previous mentioned posts in this thread your drivers are the IBM ultrium? Are you using drivers supplied by library mfg for these drives or the default windows drivers? Believe it or not, this matters
Persistent binding is nice. It, sets the device to bind in the same address everytime. At least this is how it is supposed to work in theory. But sometimes hardware changes happen, and those addresses change and Networker doesn't know there new address.
Depends on how active of a SAN network you have. We are constantly building ours out larger and larger. (In 1 datacenter we backup on average 130tb a week.) So our SAN is ever growing.
So, to tackle this whole issue, and to save yourself some headache in the long wrong, set Persistent Naming as well. It's another setting that EMC doesn't talk about as much, but until it comes into play because of drive addresses changing. The nice thing about using Persistent naming is, whether the address of the unit changes.. (ex: ADIC@2.1.1) persistent naming doesn't care because it bases it on the WWN of the drive.
If you use the windows driver MS has an article on it that I had sitting around here somewhere but can't locate at this moment, but if you use your mfg drivers, they are done by IBM. And they have there own way to set persistent naming with them as well.
I HIGHLY recommend you set the persistent naming. Here's an example of how I did my IBM driver. (I have IBM Ultrium drives as well that Dell provides.) Persistent naming is all set in the registry.
(note: the WWNN_ names has the letters in lower case, if you export this key to install and set on several servers like I did, make sure the letters stay in lower case or the device name you set won't stick and it will set it to whatever it wants.)
The last part of the key will correspond to the WWN name of your tape drive. I manually modified mine to tape names like Tape1, Tape2, etc. Because the IBM driver when persistent naming is set, creates the key and gives it a default name of Tape4801011 or something like that. IBM's idea of being cute using the hexdecial equiv of the letters IBM. I had usses with it using that name, so I manually modified it.
In here you will have:
PersistentDeviceName REG_SZ Data Value is the device name you want to give the device like Tape5
Now if your using the native Windows driver, as mentioned before, there is a similar way via the registry, to set and make the persistent naming stick as well. Also I used the persistent naming, so that every server no matter what always came up with the same tape device name no matter which server it was on.
HacknDos1
66 Posts
0
October 1st, 2009 10:00
1) Zoning is setup proper
2) Switch is hard set for 4gb and not on Auto
3) Are the tape drives in use when you are trying to do this? (belive it or not this matters.)
Inquire although useful, will display different information back to a server connected to the same drives, if those drives are in use on a different server. So make sure none of the hardware is in use.
I myself have tried to setup drives on a storage node in the past, and scratched my head as to why doesn't the server see them, and why arent they appearing in inquire, only to come and find out they were in use.
4) Open your HBA software and see if the drives appear there. If they don't, or only one of them does. You need to go back to the switch. OS won't see them if the HBA can't see them.
Paul
HCLBACKUP
150 Posts
0
September 28th, 2009 05:00
I think the drives and library is not visible at OS level itself.
pereubu
86 Posts
0
September 29th, 2009 02:00
amediratta
2K Posts
0
September 30th, 2009 02:00
If it is not there, check the hardware connectivity. reboot the server and check during boot process on the SCSI card if I think cabling is OK.
I would also recommend installing latest Autochanger & device manufacturer drivers instead of relying on Windows drivers.
pereubu
86 Posts
0
September 30th, 2009 03:00
Ok with drivers, but I have checked Connectrix and zone for that, and it seems to be OK. HBAnywhere as well. But what about SCSI card? I have on Device Manager SCSI and RAID controllers and there is EMS Device bus.
Briefly I do not have knowledge to know how to check cabling on SCSI card!
PeterBen
120 Posts
0
September 30th, 2009 04:00
HacknDos1
66 Posts
0
September 30th, 2009 11:00
If this tape drive that is the controller is not presented to the server (Management Server or Storage Node), server won't see the library. Only server to see the library would then be the machine that has that tape drive presented to it. (Zoned to that server)
Hope this helps.
Paul
aismaili
25 Posts
0
September 30th, 2009 18:00
4) Configure an SJI Jukebox
Try that and let us know.
amediratta
2K Posts
0
October 1st, 2009 00:00
Run the inquire command and check if you get the robotics and drives there. If not clear to you, post the output here.
pereubu
86 Posts
0
October 1st, 2009 06:00
C:\Documents and Settings\aleksandar>inquire -t
scsidev@0.0.0:DGC RAID 5 0326|Disk,
S/N: C
WWNN=6
PORT=0
scsidev@0.0.3:DGC RAID 5 0326|Disk
scsidev@0.1.0:DGC RAID 5 0326|Disk
scsidev@0.2.0:DGC RAID 5 0326|Disk
scsidev@0.3.0:DGC RAID 5 0326|Disk
scsidev@0.4.0:IBM ULTRIUM-TD3 64D0|Tape
scsidev@5.0.0:DGC RAID 5 0326|Disk
scsidev@5.0.3:DGC RAID 5 0326|Disk
scsidev@5.1.0:DGC RAID 5 0326|Disk
scsidev@5.2.0:DGC RAID 5 0326|Disk
scsidev@5.3.0:DGC RAID 5 0326|Disk
The same thing is on the Device manager. This is new computer and it is storage node. It works only for one drive (device). I have installed Ultrium Driver.
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\mb_admin>inquire -t
scsidev@0.0.0:DGC RAID 10 0326|Disk, \\.\PHYSICALDRIVE0
S/N: CK200071900247
WWNN=6006016049AD1C001CB0F2F72035DC11
PORT=00000001
scsidev@0.0.1:DGC RAID 5 0326|Disk, \\.\PHYSICALDRIVE1
S/N: CK200071900247
WWNN=600601602BC41D004D6E42E4F077DC11
PORT=00000001
scsidev@0.1.0:DGC RAID 10 0326|Disk
scsidev@0.2.0:DGC RAID 10 0326|Disk
scsidev@0.3.0:DGC RAID 10 0326|Disk
scsidev@0.4.0:IBM ULTRIUM-TD3 64D0|Tape, \\.\Tape0
S/N: 1210266394
ATNN=IBM ULTRIUM-TD3 12102663
94
WWNN=500308C175E80426
WWPN=500308C175E80427
PORT=00000001
scsidev@4.0.0:DGC RAID 10 0326|Disk
scsidev@4.0.1:DGC RAID 5 0326|Disk
scsidev@4.1.0:DGC RAID 10 0326|Disk
scsidev@4.2.0:DGC RAID 10 0326|Disk
scsidev@4.3.0:DGC RAID 10 0326|Disk
scsidev@4.4.0:IBM ULTRIUM-TD3 64D0|Tape, \\.\Tape1
S/N: 1210266406
ATNN=IBM ULTRIUM-TD3 12102664
06
WWNN=500308C175E80423
WWPN=500308C175E80424
PORT=00000001
scsidev@4.4.1:ADIC Scalar 24 310A|Autochanger (Jukebox), \\.\Changer0
S/N: ADIC_1_C00027529
C:\Documents and Settings\mb_admin>
That one is storage node as well, but I can have two devices (two drives on the jukebox) from this server.The Device Manager gives drive for a changer and two drives for tape. Therefore I can have two devices for each old sever configured as a storage node.
pereubu
86 Posts
0
October 1st, 2009 06:00
Try that and let us know."
I have done by the way of graphics, but by command line I was not successful.
amediratta
2K Posts
0
October 1st, 2009 09:00
Do you see the second drive & medium changer as unknown devices in Device Manager? If not, you have issues with the setup somewhere. When I had zoning done properly but devices not visible in the Device Manager, I checked that the FC ports on switch were on Auto mode. I could resolve the problem when I switched them to 4 Gbps from Auto mode.
HacknDos1
66 Posts
1
October 1st, 2009 10:00
Paul
pereubu
86 Posts
0
October 2nd, 2009 03:00
2) Switch is hard set for 4gb and not on Auto
3) Are the tape drives in use when you are trying to do this? (belive it or not this matters.)"
Zoning is Ok. Switch is DS 4700M, and the speed is 4Gb. It set for negotiate. No tape drives are not in use for sure.
4) Open your HBA software and see if the drives appear there. If they don't, or only one of them does. You need to go back to the switch. OS won't see them if the HBA can't see them.
That might be prtoblem, HBAnyware - on the first dapter. I have got message:" WWN list is not available when automap is disabled". On the target mapping I have automapping disabled. Now I have to be sure to put automapping enabled.
On th etop of that I have to think about persistant binding because I have windows 2003 servers.
HacknDos1
66 Posts
0
October 2nd, 2009 08:00
If you allow me to digress from the topic a hair here, I will give you some helpful information.
I believe from previous mentioned posts in this thread your drivers are the IBM ultrium? Are you using drivers supplied by library mfg for these drives or the default windows drivers? Believe it or not, this matters
Persistent binding is nice. It, sets the device to bind in the same address everytime. At least this is how it is supposed to work in theory. But sometimes hardware changes happen, and those addresses change and Networker doesn't know there new address.
Depends on how active of a SAN network you have. We are constantly building ours out larger and larger. (In 1 datacenter we backup on average 130tb a week.) So our SAN is ever growing.
So, to tackle this whole issue, and to save yourself some headache in the long wrong, set Persistent Naming as well. It's another setting that EMC doesn't talk about as much, but until it comes into play because of drive addresses changing. The nice thing about using Persistent naming is, whether the address of the unit changes.. (ex: ADIC@2.1.1) persistent naming doesn't care because it bases it on the WWN of the drive.
If you use the windows driver MS has an article on it that I had sitting around here somewhere but can't locate at this moment, but if you use your mfg drivers, they are done by IBM. And they have there own way to set persistent naming with them as well.
I HIGHLY recommend you set the persistent naming. Here's an example of how I did my IBM driver. (I have IBM Ultrium drives as well that Dell provides.) Persistent naming is all set in the registry.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtp2k3
In here you create:
PersistentNaming REG_DWORD set value to 1
Reboot machine after setting this and then the following keys will be created.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibmtpbs2k3\WWNN_500308c09bdc3004
(note: the WWNN_ names has the letters in lower case, if you export this key to install and set on several servers like I did, make sure the letters stay in lower case or the device name you set won't stick and it will set it to whatever it wants.)
The last part of the key will correspond to the WWN name of your tape drive. I manually modified mine to tape names like Tape1, Tape2, etc. Because the IBM driver when persistent naming is set, creates the key and gives it a default name of Tape4801011 or something like that. IBM's idea of being cute using the hexdecial equiv of the letters IBM. I had usses with it using that name, so I manually modified it.
In here you will have:
PersistentDeviceName
REG_SZ
Data Value is the device name you want to give the device like Tape5
Now if your using the native Windows driver, as mentioned before, there is a similar way via the registry, to set and make the persistent naming stick as well. Also I used the persistent naming, so that every server no matter what always came up with the same tape device name no matter which server it was on.
Hope you find this useful.
Paul
Message was edited by:
Paul Schandel
Message was edited by:
Paul Schandel